Orchestrator Blueprints

The orchestrator Keyfactor orchestrators perform a variety of functions, including managing certificate stores and SSH key stores. blueprint A snapshot of the certificate stores and scheduled jobs on one orchestrator, which can be used to create matching certificate stores and jobs on another orchestrator with just a few clicks. system allows a large number of similar orchestrators to be configured with minimal effort on the part of the user. By taking a snapshot of the certificate stores and scheduled jobs on one orchestrator, matching certificate stores and jobs can be defined on another orchestrator with just a few clicks. With an orchestrator auto-registration handler, blueprint application can even be completely automated, so that a large number of machines or devices can be configured and obtain certificates with no user input after initial configuration of the blueprint and handler. This can greatly improve security by ensuring that each device is provisioned from day one with a unique certificate using a private key Private keys are used in cryptography (symmetric and asymmetric) to encrypt or sign content. In asymmetric cryptography, they are used together in a key pair with a public key. The private or secret key is retained by the key's creator, making it highly secure. generated on the device as well as an up-to-date list of trusted roots, and it allows for continuous monitoring and reporting of all certificates across all configured devices.

Orchestrator blueprints are generated from the Orchestrator Management page (see Orchestrator Management) and applied to new orchestrators manually via the Orchestrator Management page. On the Orchestrator Blueprints page, you can review the existing blueprints, view details of a blueprint (what certificate stores and scheduled jobs are included in the blueprint), and delete blueprints.